Signaling Between Master and Slave Components Using a Shared Communication Node of the Master Component

ABSTRACT

A network slave device includes a transceiver for communicating over a communication bus in accordance with a point-to-point network protocol. The network slave device may have an address to identify the network slave device on the network. It may also have a communication circuit configured to process a series of commands received by the transceiver and respond to a command if a position of the command in the series of commands corresponds to the address of the network slave device. A master device communicating on the network may send the series of command in accordance with the point-to-point network protocol. In an embodiment, the point-to-point protocol is the SENT protocol.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part application of, and claimspriority to, U.S. patent application Ser. No. 14/182,595 (filed Feb. 18,2014), which is incorporated here by reference in its entirety.

BACKGROUND

Sensors are used to monitor various parameters of a system. For example,in vehicle systems, parameters such as current, speed, angle, linearposition, and rotational direction of an article associated with acontrol module, such as a power steering module, a fuel injectionmodule, and an anti-lock brake module, are often monitored. The sensoroutput signal is provided to a system controller, such as an EngineControl Unit (ECU), that processes the sensor output signal and maygenerate a feedback signal for desired operation of the control module.Conventionally, the sensor updates the sensed parameter periodically andthe controller polls the sensor for data as needed for processing.

SUMMARY

In an embodiment, a network slave device includes a transceiver forcommunicating over a communication bus in accordance with apoint-to-point network protocol. The network slave device may have anaddress to identify the network slave device on the network. It may alsohave a communication circuit configured to process a series of commandsreceived by the transceiver and respond to a command if a position ofthe command in the series of commands corresponds to the address of thenetwork slave device.

In another embodiment, a system includes a master device coupled to acommunication bus and configured to communicate over the communicationbus in accordance with a point-to-point communication protocol to send aseries of commands over the communication bus. One or more slave devicesmay be coupled to the communication bus to communicate over thecommunication bus in accordance with the point-to-point communicationprotocol. Each of the slave devices may have a respective address toidentify the respective slave device and may be configured to respond toa command in the series of commands that has a position within theseries that matches the respective address of the respective slavedevice.

In another embodiment, a method includes sending a series of commands bya master device coupled to a one-wire communication bus. A selectedslave device may respond to one of the commands if the position of thecommand in the series of commands matches an address of the selectedslave device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a sensor system with sensors sharinga communication node of the controller.

FIG. 2 is a block diagram showing a magnetic field sensor suitable foruse in the sensor system of FIG. 1.

FIG. 3 is a timing diagram showing the SENT signal format.

FIG. 4 is a timing diagram showing a trigger signal sent to a pluralityof sensors of FIG. 1 to illustrate the timing of sensor data storing andtransmission of the respective serial data signal by each of the sensorsunder the control of the trigger signal.

FIG. 5A is an example of a trigger signal used to retrieve data from aselected sensor.

FIG. 5B is another example of a trigger signal used to retrieve datafrom a selected sensor.

FIG. 6A is a timing diagram of an example of a first trigger signal tostore data at a sensor and a second trigger signal used to retrieve thedata from the sensor using the communication node.

FIG. 6B is a timing diagram of an example of a first trigger signal tostore data at a sensor and a second trigger signal used to retrieve thedata from the sensor using the communication node.

FIG. 7 is a timing diagram of a transmission between a master and slaveon a communication node that includes addresses.

FIG. 8 is a timing diagram of another transmission between a master andslave on a communication node that includes addresses.

FIG. 9 is a timing diagram of a transmission sequence, including asample pulse/command, between a master and multiples slaves on acommunication node.

FIG. 10 is a timing diagram of another transmission sequence, includinga sample pulse/command, between a master and multiples slaves on acommunication node.

FIG. 11 is a timing diagram of a transmission sequence, including adiagnostic pulse/command, between a master and multiples slaves on acommunication node.

FIG. 12 is a timing diagram of another transmission sequence, includinga diagnostic pulse/command, between a master and multiples slaves on acommunication node.

FIG. 13 is a timing diagram of transmission sequence, including apredetermined sequence of replies, between a master and multiples slaveson a communication node.

FIG. 14 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a reset timeout, between amaster and multiples slaves on a communication node.

FIG. 15 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies with reply delay times, between amaster and multiples slaves on a communication node.

FIG. 16 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies, between a master and multiplesslaves on a communication node.

FIG. 17 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a sample pulse/command, betweena master and multiples slaves on a communication node.

FIG. 18 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a sample pulse/command, betweena master and multiples slaves on a communication node.

FIG. 19 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a diagnostic pulse/command,between a master and multiples slaves on a communication node.

FIG. 20 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a diagnostic pulse/command,between a master and multiples slaves on a communication node.

FIG. 21 is a timing diagram of another transmission sequence, includinga predetermined sequence of replies and a counter resent pulse/command,between a master and multiples slaves on a communication node.

Like figures in the drawings denote like elements.

DETAILED DESCRIPTION

As used herein, the term “magnetic field sensing element” is used todescribe a variety of electronic elements that can sense a magneticfield. The magnetic field sensing element can be, but is not limited to,a Hall Effect element, a magnetoresistance element, or amagnetotransistor. As is known, there are different types of Hall Effectelements, for example, a planar Hall element, a vertical Hall element,and a Circular Vertical Hall (CVH) element. As is also known, there aredifferent types of magnetoresistance elements, for example, asemiconductor magnetoresistance element such as Indium Antimonide(InSb), a giant magnetoresistance (GMR) element, an anisotropicmagnetoresistance element (AMR), a tunneling magnetoresistance (TMR)element, a magnetic tunnel junction (MTJ), a spin-valve, etc. Themagnetic field sensing element may be a single element or,alternatively, may include two or more magnetic field sensing elementsarranged in various configurations, e.g., a half bridge or full(Wheatstone) bridge. Depending on the device type and other applicationrequirements, the magnetic field sensing element may be a device made ofa type IV semiconductor material such as Silicon (Si) or Germanium (Ge),or a type III-V semiconductor material like Gallium-Arsenide (GaAs) oran Indium compound, e.g., Indium-Antimonide (InSb).

As is known, some of the above-described magnetic field sensing elementstend to have an axis of maximum sensitivity parallel to a substrate thatsupports the magnetic field sensing element, and others of theabove-described magnetic field sensing elements tend to have an axis ofmaximum sensitivity perpendicular to a substrate that supports themagnetic field sensing element. In particular, planar Hall elements tendto have axes of sensitivity perpendicular to a substrate, while metalbased or metallic magnetoresistance elements (e.g., GMR, TMR, AMR,spin-valve, linear spin-valve, etc.) and vertical Hall elements tend tohave axes of sensitivity parallel to a substrate.

It will be appreciated by those of ordinary skill in the art that whilea substrate (e.g. a semiconductor substrate) is described as“supporting” the magnetic field sensing element, the element may bedisposed “over” or “on” the active semiconductor surface, or may beformed “in” or “as part of” the semiconductor substrate, depending uponthe type of magnetic field sensing element. For simplicity ofexplanation, while the embodiments described herein may utilize anysuitable type of magnetic field sensing elements, such elements will bedescribed here as being supported by the substrate.

As used herein, the term “magnetic field sensor” is used to describe acircuit that uses a magnetic field sensing element, generally incombination with other circuits. Magnetic field sensors are used in avariety of applications, including, but not limited to, an angle sensorthat senses an angle of a direction of a magnetic field, a currentsensor that senses a magnetic field generated by a current carried by acurrent-carrying conductor, a magnetic switch that senses the proximityof a ferromagnetic object, a rotation detector that senses passingferromagnetic articles, for example, magnetic domains of a ring magnetor a ferromagnetic target (e.g., gear teeth) where the magnetic fieldsensor may be used in combination with a back-biased or other magnet,and a magnetic field sensor that senses a magnetic field density of amagnetic field.

As used herein, the term “target” is used to describe an object to besensed or detected by a magnetic field sensor or magnetic field sensingelement. A target may be ferromagnetic or magnetic.

As used herein, the term “predetermined,” when referring to a value orsignal, is used to refer to a value or signal that is set, or fixed. Inembodiments, the predetermined value or signal is set in the factory atthe time of manufacture, or by external means, e.g., programming,thereafter. As used herein, the term “determined,” when referring to avalue or signal, is used to refer to a value or signal that isidentified by a circuit during operation, after manufacture.

As controllers operate at faster speeds, in many cases considerablyfaster than the sensor, it becomes advantageous for the controller tosynchronize the sensor output data transmission so that the newestavailable data is provided for use by the controller. Not only issynchronizing the sensor output data transmission important but also thesynchronization of the sampling of the sensor data when multiple sensorsare used is important. Thus, information from multiple sensors may bederived with data sourced from the same moment in time.

Described herein are techniques for slave components to share a singlecommunication node of a master component. In one example, multiple slavecomponents respond in turn to one trigger sent from the communicationnode to the slave components. A trigger signal may also be referred toas a command signal. In another example, the slave components hold theirdata in response to the one trigger sent from the communication node andthe data is read at a later time by another trigger signal. The data maybe read using a Manchester encoded input that is sent from thecommunication node and is used to select a specific slave component forresponse. The data may also be read using a point-to-point serial dataprotocol (i.e. a single master and single slave protocol) such as a SENTmessage, for example.

Though sensors are used herein to represent slave components, one ofordinary skill in the art would recognize that there are other examplesof slave components that may be used. Also, other sensors, controllersand other system embodiments not specifically described herein aredescribed in U.S. Pat. No. 8,577,634, entitled “Systems and Methods forSynchronizing Sensor Data,” which was issued Nov. 5, 2013 and has thesame assignee as the present patent application and is incorporatedherein in its entirety.

Referring to FIG. 1, a system 10 includes sensors 14 a-14N configured tosense a parameter associated with an article 18 that may be controlledby a control module 12. Each of the sensors 14 a-14N has a respectivebidirectional node 16 a-16N and is configured to generate, update, andoptionally store (e.g., latch) sensor data. The sensors 14 a-14N alsoare configured to communicate sensor data to a communication node 21 ofa system controller 20 in a respective serial data signal 26 a-26N fromthe respective bidirectional node 16 a-16 n in response to a triggersignal 24 from the communication node 21 of the controller 20 andreceived at the respective bidirectional node 16 a-16N. The sensors 14a-14N are further coupled to the controller 20 via a power, or VoltageBias, Vcc connection 25. The controller 20 may provide a feedback signal22 to the control module 12 for use in controlling the article 18.

The sensors 14 a-14N may additionally store the sensor data in responseto the trigger signal. Communication buses, OUT1, OUT2, . . . OUTN, maybe coupled between the sensor 14 a-14N and the communication node 21 ofthe controller 20. As will be described further herein each of thesensors 14 a-14N is configured to at least monitor signals from theother sensors 14 a-14N accessing the communication node 21. Thus, thecommunication node 21 is a shared node. One of ordinary skill in the artwould recognize that the communication node 21 may be also a shared bus.

With this arrangement, communicating sensor data is synchronized by thetrigger signal 24 received at the bidirectional nodes 16 a-16N, whichare the same nodes at which the sensor output data are provided in theserial data signals 26 a-26N. Sensor data synchronization in this mannercan reduce sensor output data latency and also reduces the number ofsensor connections otherwise required to permit receipt of an externalsynchronization signal by the sensor. A reduced pin count not onlyreduces cost and circuit area, but also reduces effects ofelectromagnetic interference (EMI). In some embodiments in which boththe data storing function and the output data transmission function aresynchronized in this manner, ambiguities in the age of the sensor outputdata can be reduced or eliminated (e.g., multiple sensors are told tosample their data at the same time using a single trigger).

The sensors 14 a-14N may sense various parameters of an article 18,including, but not limited to current, speed, angle, linear position,turns count (e.g., for angular sensors or steering wheel applications)and rotational direction. For example, the control module 12 may be avehicle power steering module, in which case the article 18 may be amagnet associated with the steering unit and the sensor 14 a may sensethe strength of a magnetic field associated with the magnet for use bythe controller 20 to determine an angle of the wheel or steering column.In another example, the control module 12 may be a fuel injection modulein which case the article 18 may be a camshaft gear and the magneticfield strength associated with the gear can be sensed by the sensors 14a-14N and used by the controller to determine the speed of rotationand/or the rotational position of the gear. More generally however, thesensors 14 a-14N sense a characteristic associated with the article,such as magnetic field strength in the illustrative embodiments, and thecontroller 20 processes the sensor output data to arrive at the desiredparameter information, such as speed or direction of rotation. It willbe appreciated by those of ordinary skill in the art that the conceptsdescribed herein have applicability to various systems, sensors,articles, control modules, sensed characteristics, and parameters,including closed loop systems as shown and open loop systems.

The controller 20 may take various forms depending on the sensor system10 and its application. For example, in the case of a vehicle system,the controller 20 may be an Engine Control Unit (ECU) that includes aprocessor 30, a memory 32, and a transceiver 34 for controlling variousaspects of vehicle safety and operation.

The serial data signals 26 a-26N provided by the sensors 14 a-14N at thesensor bidirectional nodes 16 a-16N have a standard unidirectionalsignal format. Suitable unidirectional signal formats includeSingle-Edge Nibble Transmission (SENT), Serial Peripheral Interface(SPI), Peripheral Serial Interface 5 (PSIS) and Inter-Integrated Circuit(I²C). In the illustrative embodiment, the serial data signals 26 a-26Nis in the SENT format as defined by a Society of Automotive Engineers(SAE) J2916 Specification which is hereby incorporated by reference inits entirety and as described generally in connection with FIG. 3. Inone example, the serial data signal includes one or more of a serialbinary signal and a pulse width modulated (PWM) signal. However, theserial data signal may include other formats as well, as will bediscussed below.

Each of the sensors 14 a-14N may sense the same characteristic of asingle article 18 associated with a single control module 12 as may bedesirable for redundancy or in sensor systems in which multiple sensorsare necessary to provide the desired data, such as for directiondetection and angle detection with multiple CVH sensor die.Alternatively, each sensor 14 a-14N may sense a different characteristicassociated with the same or different articles, which articles areassociated with the same or with different control modules.

As noted above and described below, the sensor data is communicated in aserial data signal (e.g., 26 a-26N) in response to detection of atrigger signal (e.g., 24) (sent from a communication node (e.g., 21) ofa controller (e.g., 20)), received at the bidirectional node (e.g., 16a-16N) and optionally is additionally stored in response to detection ofthe trigger signal. In embodiments in which both sensor data storing andtransmission functions occur in response to the trigger signal, the datastoring and data communication functions may occur in response todetection of same feature of the trigger signal 24, resulting in commoncontrol of the storing and data communication functions by the triggersignal 24. Alternatively, the sensor data may be stored in response todetection of a first feature of the trigger signal 24 and the storeddata may be communicated in the serial data signal 26 a-26N in responseto detection of a second feature of the trigger signal 24, resulting inindependent control of the storing and data communication functions bythe trigger signal 24. Such independent control functions may beparticularly advantageous in systems in which a plurality of sensors areused (e.g., for redundancy) to sense the same parameter, since it may bedesirable to have all of the sensors sample and store (i.e., hold) thesensor data at the same time, but communicate the stored sensor data atdifferent times as best suited for processing by the controller.

Referring also to FIG. 2 in which like elements are labeled with likereference characters, an illustrative sensor 14 a includes a sensingelement 40, here a magnetic field sensing element, such as a Hall Effectelement (e.g., a circular vertical Hall). Other types of magnetic fieldsensing elements such as magnetoresistive elements (for example, a giantmagnetoresistance (GMR) element, an anisotropic magnetoresistance (AMR)element, a tunneling magnetoresistance (TMR) element, a magnetic tunneljunction (MTJ) element, a spin valve element, an Indium antimonide(InSb) sensor, a Gallium Arsenide (GaAs) sensor), and circular verticalHall Element are also suitable. Furthermore, the sensing element 40 maysense other types of characteristics such as temperature, pressure andso forth. The sensing element 40 may be a single ended or differentialarrangement and may include one or more individual sensing elements invarious known configurations.

The magnetic field sensing element 40 is coupled to interface signalprocessing circuitry which may include one of more of the followingcircuits and which generates sensor data that is provided to thecontroller 20 (FIG. 1) via the serial data signal 26 a. An amplifier 44allows for setting the magnetic field range to be sensed and a furtheramplifier 48 may permit a course adjustment of the offset. In oneillustrative embodiment, the magnetic field range may be selected to bebetween approximately +/−100 Gauss to +/−2250 Gauss. Offset refers tothe degree to which the sensed magnetic field signal (i.e., the outputof the sensing element 40) is centered at zero magnetic field. An outputof the amplifier 48 is filtered, here by an anti-aliasing filter 52, toprovide a filtered signal to an analog-to-digital (A/D) converter 56that receives a precision reference voltage from reference 64 and aclock signal 138 from a clock generator 136, as shown. Here, the A/Dconverter 56 includes a first converter 56 a configured to provide a12-bit output indicative of the level of the sensed magnetic field to afurther filter, here a low pass filter 60.

The sensor 14 a may include a temperature compensation circuit 70 tocompensate the sensed magnetic field signal for changes due totemperature. To this end, a temperature sensor 68 senses an ambienttemperature of the sensor 14 a and provides an analog signal indicativeof the temperature to an A/D converter 56 b, as shown. Converter 56 bprovides, for example, a 12-bit output signal indicative of the ambienttemperature to the temperature compensation circuit 70. In theillustrative embodiment, the temperature compensation circuit 70implements a polynomial fit of the temperature signal from converter 56b to a temperature correction equation in order to cancel thedeleterious effects of temperature variations on device sensitivity andoffset, where sensitivity refers to a change in output signal level perchange in Gauss level.

An output of the temperature compensation circuit 70 is coupled to again/offset trim circuit 74 which may employ various conventionaltechniques for gain and offset adjustment. A linearization circuit 78 isused to linearize the sensor output in response to non-linear magneticfields. To this end, the output signal range is divided into apredetermined number of segments, such as thirty-two equal segments, andthe linearization circuit 78 applies a linearization coefficient factorto each segment. The linearization coefficients may be stored in alook-up table in an EEPROM as described in U.S. Pat. No. 8,350,563,which is entitled “Magnetic Field Sensor and Method Used in a MagneticField Sensor that Adjusts a Sensitivity and/or an Offset OverTemperature” and issued Jan. 8, 2012 and has the same assignee as thepresent patent application and is incorporated herein in its entirety.

A clamp circuit 82 coupled to the output of the linearization circuit 78permits signal limiting and provides digital sensor data thus processedto the latch 86.

A latch 86 receives and stores (i.e., latches) digital sensor data fromthe interface circuitry. The latch 86 may be responsive to a triggersignal (e.g., 24, FIG. 1) received at the bidirectional node 16 a tocause the digital sensor data to be stored. More particularly, abuffered version of the trigger signal 24 (i.e., signal 106) is providedto a control node 88 of the latch 86 and contains the buffered triggersignal for detection by the latch 86. In other embodiments, the data isstored by the latch 86 independently of the trigger signal 24. An outputnode of the latch is coupled to an encoder 90, as shown.

The encoder 90 is configured to communicate the sensor data, heredigital sensor data, in the serial data signal 26 a at the bidirectionalnode 16 a in response to the trigger signal 24 received at thebidirectional node 16 a. In the illustrative embodiment, the serial datasignal 26 a has a standard unidirectional signal format and, inparticular has the SENT format. More particularly, signal 106 providedby the transceiver to a control node 92 of the encoder contains thetrigger signal for detection by the encoder. The encoder 90 provides theserial data signal 26 a at the bidirectional sensor node 16 a via atransceiver 94.

In view of the above description, it will be apparent that in theillustrative embodiment, the latch 86 stores digital sensor data inresponse to the trigger signal 24 and the serial data signal 26 a is adigital signal. However, it will be appreciated by those of ordinaryskill in the art that alternatively, the sensor data may be storedand/or communicated to the controller 20 in analog form, by analogcircuitry and techniques accordingly.

It will also be appreciated by those of ordinary skill in the art thatthe sensor data may not be “sampled and stored” in a conventionalfashion with a dedicated storage device. In one example, the latch 86may be eliminated and the trigger signal 24 in the form of bufferedsignal 106 may be provided to a control node of the A/D converter 56 a(as shown in phantom in FIG. 2), in which case generating and/orupdating of the sensor data occurs in the A/D in response to the triggersignal 24, as may be advantageous.

The sensor 14 a includes an EEPROM 100 in which programmable registersstore user selections for programmable features. In other embodiments,sensor 14 a may include another type of memory, such as a FLASH memory,random access memory (RAM), or other type of read-only memory (ROM),replacing or in addition to EEPROM 110. In embodiments, EEPROM 100and/or the other type of memory may be an on-chip memory, i.e. a memorythat is supported by a semiconductor substrate that may be the samesemiconductor substrate that supports the various circuits comprisingsensor 14 a. Various schemes are suitable for programming communicationbetween the controller 20 and the sensor 14 a.

A Manchester encoding scheme may be used with which the controller 20sends commands to the sensor 14 a via the Vcc connection 25, such as aWrite Access Command, a Write Command, and a Read Command. In responseto a Read Command, the sensor 14 a may respond with a Read Acknowledgesignal via bus OUT1 that contains the requested data.

Each senor may include a transceiver for communicating over acommunication bus in accordance with a point-to-point network protocol,an address to identify the network slave device, and a communicationcircuit configured to process commands received by the transceiver andgenerate a reply for transmission over the communication bus if anaddress included in the command matches the address of the slave device.The address may be stored in a memory of the sensor, such as an EEPROMfor example.

A communication circuit and transceiver including a serial decoder 110translates the Vcc signal level (e.g., having a signal of 5-8 volts)into a logic signal and a serial interface 112 decodes the resultinglogic signal into a binary command signal. For example, in the case of aWrite Command, the binary command signal at the output of the serialinterface 112 indicates to an EEPROM controller 108 the address of theregister to be written and the data to be written. A Write AccessCommand unlocks the device for writing. In the case of a Read Command,the binary signal output of the serial interface 112 presents thecontents of the selected register to the transceiver for communicationat the bidirectional node 16 a.

In order to write to the EEPROM, the controller 20 (FIG. 1) sends aDisable Output Command to put the bidirectional node 16 a into a highimpedance state. The controller 20 also sends high voltage pulses to thesensor in order to boost the voltage on the EEPROM gates. To this end, apulse detector 98 is coupled to the bidirectional node 16 a and to theEEPROM controller 108. After writing is complete, the controller 20sends an Enable Output Command to bring the bidirectional node 16 a fromits high impedance state to a value indicative of the sensed magneticfield. Preferably, the bidirectional node 16 a is also put into a highimpedance state before a Read Command is sent until after the ReadAcknowledge signal is returned.

Various features of the sensor 14 a are programmable in theabove-described manner, including but not limited to the magnetic fieldrange via amplifier 44, the course offset trim via amplifier 48, thebandwidth via filter 60 and so forth. According to the invention, asensor data communication mode is also programmable. Specifically, thesensor 14 a can be programmed to dictate whether the sensor data iscommunicated to the controller in a conventional manner (independent ofany synchronization by the controller) or according to the invention (inresponse to receipt of the trigger signal 24 from the controller 20 atthe sensor bidirectional node 16 a). Additional programmable featuresrelate to the SENT signal format as described below.

Additional features of the sensor 14 a may include anundervoltage/overvoltage lockout circuit 120 and a power-on reset (POR)circuit 124. The undervoltage/overvoltage lockout circuit 120 senses thevoltage level of the Vcc signal 25, sending an error signal to theMaster Control block 104 if a predetermined range is exceeded (Forexample, it is these types of faults, along with temperature sensorinformation that may be read out of an addressed device over the maininterface (SENT). In addition, specific registers/EEPROM in theaddressed/shared device may also be written to). The POR circuit 124pauses critical circuitry upon power-up until Vcc reaches an appropriatevoltage level.

The sensor 14 a may be provided in the form of an integrated circuit,here with an analog front-end portion 140 and a digital subsystem 144.An analog voltage regulator 128 provides a regulated voltage to theanalog front-end 140 and a digital regulator 132 powers the digitalsubsystems 144, as shown. Clock generator 136 provides clock signals tothe A/D converter 56 and to the master controller 104. It will beappreciated by those of ordinary skill in the art however, that theparticular delineation of which circuit functions are implemented in ananalog fashion or with digital circuitry and signals can be varied. Alsocircuit functions that are shown to be implemented on the integratedcircuit sensor 14 a can be accomplished on separate circuits (e.g.,additional integrated circuits or circuit boards).

Referring also to FIG. 3, the serial data signals 26 a-26N communicatedby the sensor 14 a-14N may have a standard unidirectional signal format,such as the illustrative SENT signal format. A SENT signal 150 consistsof a sequence of pulses which is repeatedly sent by the transmittingmodule (here, the sensor 14 a). A traditional SENT signal 150 mayinclude at least four portions: a Synchronization/Calibration portion152, a Status and Serial Communication portion 154, a Data portion 158,and a Checksum (or cyclic redundancy check, CRC) portion 160. A “tick”refers to the nominal clock signal period and a “nibble” is 4 bits. Eachnibble has a specified time for low and high state. The low stateduration is by default 5 ticks and the high state duration is dictatedby the information value of the nibble. The Synchronization/Calibrationportion 152 identifies the start of the SENT message and always has apulse duration of 56 ticks. Status and Serial Communication portion 154is used to inform the controller 20 of the sensor status or features(such as part numbers or error code information) and has a duration ofbetween 12 and 27 ticks to provide 4 bits. The Data portion 158 includesup to six nibbles of data, with each nibble containing 4 bits withvalues ranging from 0 to 15. Thus, each data nibble has a pulse durationfrom 12 to 27 ticks. The number of data nibbles will be fixed for eachapplication but can vary between applications. In order to transmit two12 bit values, 6 data nibbles are communicated, as shown.

The SENT signal 150 includes an optional pause portion 164 that is usedin connection with the invention in order to permit bidirectionalcommunication via the bidirectional sensor node 16 a. In general, thepause portion 164 corresponds to a period of inactivity on the outputbus, OUT1, (FIG. 1) or in other words, a time when the serial datasignal 26 a (FIG. 1) is inactive or high. Conventionally, the pauseportion 164 is sometimes used to prolong the SENT signal to a constantlength if desired. The user can program a particular desired frame ratevia the programming scheme as described above. It will be appreciated bythose of ordinary skill in the art that inactivity on the output bus,OUT1, may alternatively correspond to a low (pull down) signal level.

According to the invention, the pause portion 164 is used to permitbidirectional communication on the output bus, OUT1, by allowing for thetrigger signal 24 received at the sensor bidirectional node 16 a duringthe pause portion to control data functions of the sensor. It will beappreciated by those of ordinary skill in the art that the SENT signalpause portion 164 represents a part of the signal when neither data norcontrol information is transmitted by the sensor and thus, may bereferred to more generally as the inactive transmission portion 164.

Various aspects of the SENT signal format can be user programmed, forexample, in the EEPROM 100 of FIG. 2. As examples, a SENT_STATUSparameter can be used to indicate the desired format for the four bitStatus and Serial Communication portion 154, a SENT_SERIAL parameter canbe used to select a desired format for a serial data signal embedded insuccessive SENT messages according to the SENT specification, comprisinga short serial message format of 8 bits, an enhanced serial messageformat of 12 bits, or a further enhanced serial message format of 16bits. A SENT_DATA parameter can be used to specify the particular sensordata to be communicated in the data nibbles. For example, one value ofthe SENT_DATA parameter may indicate that three data nibbles representmagnetic field data and three data nibbles represent temperature data. ASENT_TICK parameter can used to specify the nominal tick time. ASENT_LOVAR parameter can be used to depart from the SENT standard ofhaving a fixed low state time in each nibble to having the high statetime fixed instead. And a SENT_FIXED parameter can be used to departfrom the SENT standard by specifying a different defined length of thefixed portion of each nibble.

A SENT_UPDATE parameter is used to specify a desired data communicationmode. In one mode of data communication, sensor data is stored inresponse to detection of a first feature of the trigger signal 24 and iscommunicated in response to a detection of second feature of the triggersignal 24 (see, for example, FIG. 5). In other examples, sensor data isboth stored and communicated to the controller 20 (FIG. 1) in responseto detection of a single feature of the trigger signal 24. Other datacommunication modes are also possible, such as a mode in which thetrigger signal controls only generating/updating the sensor data (suchas via the A/D converter 56 of FIG. 2), a mode in which the triggersignal only controls communication of the serial data signals 26 a-26Nand any sensor data generating/updating and/or dedicated sensor datastorage occurs independently of the trigger signal, a mode in which thetrigger signal resets certain sensor circuitry (such as clock generator136, registers, or counters) such as a mode in which any combination ofthese sensor functions is controlled by the trigger signal, or a mode inwhich the serial data signal 26 a does not include the optional pauseportion 164. For example, the trigger signal may, alternatively, controlonly one such function (data sampling, storing or communication) or anycombination of sensor data storing, updating, resetting and transmittingfunctions.

Referring also to FIG. 4, in one mode of data communication, sensor datais stored in response to detection of a trigger signal received at thesensor bidirectional node and is communicated to the controller. FIG. 4shows a signal transmission 171 from the controller 20 to the sensors 14a-14N for the sensor system 10 (FIG. 1). Each sensor 14 a-14N isresponsive to a first feature 210, shown in FIG. 4 as a falling edge, ofa received trigger signal 96 for storing sensor data and to a secondfeature 214, shown in FIG. 4 as a rising edge, of the received triggersignal for transmitting the stored sensor data in a serial data signal.The first feature 210 may be used by sensors (e.g., linear and anglesensors) as a trigger mechanism to multiple devices to trigger thesampling of data by the sensors.

The sensors 14 a-14N detect the first feature 210 a of the triggersignal, here a falling edge, samples and stores their respective sensordata in the latch 86 in response. The sensors 14 a-14N further detectthe second feature 214 a of the trigger signal, here a rising edge. Eachsensor 14 a-14N responds in turn (sequentially) based on a previouslyconfigured order. In one particular example, sensor 14 a sends a SENTmessage 224 a; after sensor 14 a sends the SENT message 224 a, thesensor 14 b sends a SENT message 224 b; and so forth with the sensor 14Nsending the last SENT message 224N.

The first sensor in the previously configured order would respond with aserial data signal while the remaining sensors start monitoring theserial data signals from the other sensors to determine when it may sendits message. In one example, the previously configured order would bestored in the EEPROM or another type of non-volatile device. In oneexample, in the event that a next sensor determines that there is nomessage within a specified amount of time coming from the previoussensor in the previously configured order, the next sensor responds withits serial data signal and a notification that it did not detect themessage from the previous sensor. In one example, each sensor may reportits identification (address or identifier bit stream) in its StatusNibble. In other examples, based on an address of a particular devicethe sensor could provide more than just Hall magnetic field data. Thesensor could, for example, further provide temperature sensor data orerror flag status if in a read mode command.

In other examples, the sensors 14 a-14N would listen to the messagessent by the other sensors. For example, the sensors may compare theiroutput values and register a plausibility error if the sensor's valuesshould be matched. In other examples, other information may be comparedsuch as temperature values between sensors.

While the trigger signal features used in this embodiment are signaledges of a particular direction, various other signal features wouldalternatively be used, including but not limited to one or more signalpulses (i.e., detection of first and second, opposite edge directions),multiple edge detections of the same or different directions and soforth.

In other examples, a trigger signal from the controller 20 does notnecessitate a response from the sensor components 14 a-14N that includesdata. In one example, no response is required. In another example, thesensor components 14 a-14N may send a response that does not includedata; but rather, the response is, for example, an acknowledgment signalthat indicates that the trigger signal was received by the sensor.

In one particular example, a trigger signal may include a number oftoggling pulses issued from the controller where the pulses areseparated by a small number of ticks. In another particular example, atrigger signal may be used that includes an address not used by thesensors 14 a-14N. In one particular example, sensors have addresses 00,01 and 10; and 11 is used as a trigger signal. For example, the triggersignal would instruct all devices to sample the magnetic field level atthis specific time.

Referring to FIG. 5A, if the trigger signal instructs the sensors 14a-14N to store their data but not send the data to the controller 20,then an additional trigger signal is used to retrieve the data. Inparticular, a second trigger signal may be directed at one specificsensor or a subset of the sensors 14 a-14N. For example, the secondtrigger signal may be a Manchester encoded signal. The sensors 14 a-14Nreceiving signals from the communication node 21 will listen to theencoded signal and if a sensor recognizes that it is being addressedsends its data. For example, the sensor sends a serial data signal. FIG.5A depicts one particular example, where two zeroes are transmitted in arow followed by a 2-bit sensor address flowed by a portion to allow thesensor response.

Referring to FIG. 5B, in another particular example, the address bitsmay be extended from just 2 bits to, for example, 8 bits, to addressinternal registers in a sensor device. For example, the first 2 bits ofthe Address field could be for addressing the particular slave device,the next 2 bits bit could be used to indicate a coded Read/Writemessage, and then the remaining 4 bits could be used for addressing aninternal register/EEPROM in the device.

Referring to FIG. 6A, in another example of retrieving data from thesensors 14 a-14N, a serial data signal message may be sent from thecontroller 20 to the sensors 14 a-14N but intended for one of thesensors. For example, the serial data signal may be a SENT message asdescribed in FIG. 3. The selected sensor would interpret the SENTmessage in the same manner the controller 20 would. FIG. 6A depicts atransmission signal 300 that includes a falling edge 310 which signalsthe sensors 14 a-14N to store their data. The controller 20 sends a SENTmessage 324 that triggers one of the sensors 14 a-14N to respond bysending its data in a SENT message 336. For example, the SENT message isthe SENT signal 150 described in FIG. 3 that includes fifty-six ticksfor synchronization followed by one or more Nibbles. In one example, theSENT message 324 from the controller 20 includes an address of thedesired sensor to respond. For example, a Nibble may include a 4-bitaddress. In one example, the SENT message 324 may include a cyclicredundancy check (CRC).

Referring to FIG. 6B, in another example, a transmission signal 400 thatincludes a falling edge 410 which signals the sensors 14 a-14N to storetheir data. The controller 20 sends a Manchester message 424 (e.g., suchas described in FIGS. 5A and 5B) that triggers one of the sensors 14a-14N to respond by sending its data in a SENT message 436.

Referring to FIG. 7, serial data communication 700 between controller 20acting as a master and a sensor acting as a slave may be transmitted inaccordance with a point-to-point (i.e. single master and single slave)protocol, such as the SENT protocol. In this example, the sensor mayhave address “1” and be configured to respond to communications fromcontroller 20 that include address “1”. For clarity, the sensor withaddress 1 may be referred to as “sensor 1,” the sensor with address 2 as“sensor 2,” etc.

The controller 20 sends a command to a slave device, in this example asensor. The command may include a request pulse and an address,requesting that the sensor with the matching address send its data tocontroller 20. The command may begin with controller 20 sending arequest pulse 702 onto the bus (e.g. onto bidirectional nodes 16 a-16N).Following request pulse 702, controller 20 may send an address 704 thatidentifies one or more of the sensors on the bus. The address may be aseries of toggling pulses that identify a sensor or, in anotherembodiment, the address may be a single pulse having a duration thatcorresponds to one of the sensors. In the former case, each sensor isassociated with a unique count value of pulses and/or pulse edges ortransitions and the sensor associated with the number of pulses and/orpulse edges of the transmitted address may respond to controller 20. Inthe latter case, each sensor is associated with a unique duration andthe sensor associated with the duration of the transmitted address pulsemay respond to controller 20.

In the example shown in FIG. 7, controller 20 sends a single high pulse706 and a single low pulse 708 to indicate it is requesting a responsefrom the sensor with the address “1.” The address 704 is followed by anend signal 710 indicating the end of the message. To generate end signal710, controller 20 may hold the voltage on the bus high (oralternatively low) for a predetermined period of time that is greaterthan the duration of an address pulse (e.g. a duration greater than thatof address pulse 706 or 708).

After receiving request 702, each of the sensors may count the number oftoggle pulses within address 704. Alternatively, each sensor may countthe number of falling and/or rising edges of address signal 704. Whenthe sensors receive end signal 710, each sensor may determine whetherthe address (i.e. the count) matches its own address. The sensor withthe matching address may then respond to the request by sending data 712to the controller.

In FIG. 8, serial data communication 800 includes an end signal 802 thatis pulled low on the bus. Similarly to FIG. 7, controller 20 may send arequest signal 804 followed by an address signal 806. Address signal 806may include a series of toggling pulses indicating an address of one ormore of the sensors. Following address signal 806 is end signal 802. Inthis example, to generate end signal 802, controller 20 pulls the buslow for a predetermined period of time. The duration of the end signalmay be longer than the duration of the pulses of address signal 806 todifferentiate the end signal from one of the address pulses. Because endsignal 802 is pulled low, only one pulse is needed in address signal 806to indicate the address of “1”. If controller 20 were addressing thesensor with address “3”, for example, then controller 20 may send threepulses onto the bus.

After receiving request 804, each of the sensors may count the number oftoggle pulses within address signal 806. Alternatively, each sensor maycount the number of falling and/or rising edges of address signal 806.When the sensors receive end signal 802, each sensor may determinewhether the address matches its own address. The sensor with thematching address may then respond to the request by sending data 808 tothe controller.

Referring now to FIG. 9, a transmission sequence 900 may include aseries of requests from controller 20 for data from sensors 14 a-14N.Transmission sequence 900 may begin with a sample pulse 902, which maybe a broadcast message (i.e. a message or command that is sent to allthe slave devices on the bus). Sample pulse 902 may act as a commandinstructing any or all sensors 14 a-14N to perform a measurement.Synchronous sample pulse 902 may be a pulse that is pulled low, oralternatively pulled high, and may have a predetermined or knownduration in ticks. When received by sensors 14 a-14N, the pulse may actas a command that causes sensors 14 a-14N to sense and record thecharacteristic (e.g. the magnetic field) of the article, as describedabove. The sensors may then store the measurement in an internal memoryor register for later transmission.

After sample pulse 902, controller 20 may request the sensors send themeasurement to controller 20. In the example shown, after sample pulse902 is sent, controller 20 sends a request pulse 904 onto bidirectionalnodes 16 a-16N. To send request pulse 904, controller 20 may pull thevoltage on bidirectional nodes 16 a-16N low (or alternatively high) fora predetermined amount of time.

Following each request pulse, controller 20 may send an address toindicate which sensor should reply by sending its measurement. Theaddress may be a series of toggling pulses on the bus. For example,address “1”, following request pulse 906, may comprise one toggle: onehigh pulse 908 followed by one low pulse 910. The address “2”, followingrequest pulse 912, may comprise two toggles: a high pulse 914, followedby a low pulse 916, followed by another high pulse 918, followed byanother low pulse 920. The address “3” may comprise three toggles, theaddress “4” may comprise 4 toggles, and so on. Each of these togglepulses may have a predetermined duration. After the address is sent,controller 20 may send an end signal, as described above. The address“0” may comprise zero toggles, as shown by the lack of toggles followingsample pulse 904. In this case, sample pulse 904 may be followedimmediately by an end signal, such as end signal 710 and 802 in FIGS. 7and 8.

Each sensor may receive the request pulses, addresses, and end signaland determine whether the address matches its own address. The sensorwith the matching address may respond to the request by sending dataonto the bus to be received by controller 20. For example, as shown inFIG. 9, after address 0 is sent, sensor 0 responds by sending data 922onto the bus; after address 1 is sent, sensor 1 responds by sending data924 onto the bus; and so on.

Although the addresses sent from controller 20 are shown in ascendingorder (i.e. address “1”, then address “2”, then address “3”, etc.),controller 20 may address the sensors in any desired order. Regardlessof the order, the sensor with the matching address may respond. Inanother embodiment, a predetermined order of addresses may be required.

Similarly, in an embodiment, the sample pulse 902 need not appear at thebeginning of the transmission sequence. Referring to FIG. 10, similar totransmission sequence 900, a transmission sequence 1000 may include aseries of requests from controller 20 for data from sensors 14 a-14N. Asshown, controller 20 sends a sample pulse 1002 between command 1004 andcommand 1006. Sample pulse 1002 may instruct all the sensors to take ameasurement, as described above. After sample pulse 1002 is sent,controller 20 may continue sending requests for data to the sensors.

In an embodiment, sample pulse 1002 may replace the request pulse (e.g.request pulse 702 in FIG. 7) that controller 20 would otherwise send inorder to request data from the sensor. Replacing the request pulse withthe sample pulse, rather than sending a sample pulse followed by arequest pulse, can decrease communication time on the bus.

In another embodiment, appending the sample pulse 1002 with an addressmay instruct only the sensor with a matching address to make ameasurement. In this case, sampled pulse 1002 followed by address 2 maycause only the sensor with address 2 to perform a measurement.

Referring now to FIG. 11, controller 20 may send a diagnostic command tothe sensors instructing the sensors to initiate self-tests (alsoreferred to as self-diagnostic tests). In an embodiment, the diagnosticcommand comprises diagnostic pulse 1102. Controller 20 may transmitdiagnostic pulse 1102 by holding the bus low (or alternatively high) fora predetermined duration. The duration of diagnostic pulse 1102 may bedifferent from the duration of sample pulse 902 to differentiate thetypes of pulses or other types of messages or commands. When the sensorsreceive diagnostic pulse 1102, each sensor may perform self-diagnostictests to determine whether the sensor is operating properly. To allowthe sensors enough time to perform diagnostic tests, diagnostic pulse1102 may be followed by diagnostic time 1103, where controller 20 doesnot send any additional requests. The duration of diagnostic time 1103may be a predetermined time sufficient to allow the sensors to performand complete their diagnostic tests. Sending diagnostic pulse 1102followed by diagnostic time 1103, rather than followed by an address ofa specific sensor, may indicate that all sensors on the bus shouldperform self-diagnostic tests.

Following diagnostic time 1103, controller 20 may send commands to thesensors (e.g. command 1104 addressed to the sensor with address “0” andcommand 1106 addressed to the sensor with address “1”). The addressedsensors may respond by transmitting data (e.g. data transmission 1108and data transmission 1110) to controller 20. In an embodiment, the datatransmissions 1108 and 1110 sent by the sensors after receivingdiagnostic request 1102 may include the results of the diagnostic tests.Upon receipt of these results, controller 20 may determine which sensorshave passed and which have failed their diagnostic tests. If any sensorshave failed the test, controller 20 can raise an alarm or alert. Forexample, in an automotive environment where one or more of the sensorsis coupled to an automotive system such as an anti-lock braking system(“ABS”), controller 20 may send an alarm to the automobile's computerwhich can then disable the ABS, initiate a warning to the driver, ortake any other appropriate action.

Sending diagnostic pulse 1102 followed by diagnostic time 1103, ratherthan followed by an address of a specific sensor, may indicate that allsensors on the bus should perform self-diagnostic tests. In contrast,sending a diagnostic pulse followed by an address may indicate that onlythe sensor with the matching address should perform self-diagnostictests.

Referring to FIG. 12, diagnostic pulse 1202 may be followed by anaddress 1204. In an embodiment, when the diagnostic pulse and addressare received by the sensors, only the sensor with the matching addresswill initiate self-diagnostic tests. In the example shown, address 1204is the address “1”. Thus, when diagnostic pulse 1202 and address 1204are received, the sensor with address “1” will perform self-diagnostictests while the other sensors continue to operate normally.

While the sensor 1 is performing diagnostic tests, controller 20 maysend one or more requests to the other sensors, such as request pulse1206 sent to the sensor with address “0”. The sensor with the matchingaddress may respond with data transmission 1208 (which may includemeasurement data or other requested data). After diagnostic time 1210has elapsed, controller 20 may send command 1212 to sensor 1, and thesensor may respond by sending data 1214 with the results of itsdiagnostic tests to controller 20. In an embodiment, after a sensorreceives a diagnostic pulse 1102 or 1202, the next data sent by thesensor will include its self-diagnostic test results.

Referring to FIG. 13, controller 20 may send requests without addressesto the sensors. In such an embodiment, the sensors may each have anaddress, and may respond to a command in the sequence if the position ofthe command within the sequence matches the sensor's address. Intransmission sequence 1300, controller sends a series of trigger pulses1302 a-1302N. After each trigger pulse, a sensor responds in apredetermined order. For example, after the first trigger pulse 1302 a,the sensor with address 1 responds by sending data 1304 a, after thesecond trigger pulse 1302 b, the sensor with address 2 responds bysending data 1304 b, and so on. After all the sensors have sent theirdata, the sequence may repeat.

In an embodiment, each sensor has knowledge (e.g. data stored in amemory or register) of how many sensors are operating on the bus. Eachsensor may also include a counter to count the number of trigger pulsessent by controller 20. After each trigger pulse 1302 a-1302N, thesensors may increment their counter to keep track of the number oftrigger pulses sent. If a sensor receives a trigger pulse 1302 a-1302N,and the sensor's counter matches the sensor's address, that sensor mayrespond to the trigger pulse by sending its data to controller 20. Thus,the sensors may respond to requests from the controller 20 in around-robin manner.

Each of the sensors' counters may be configured to reset when the countreaches or exceeds the number of sensors that are active on the bus.After all the sensors on the bus have responded to requests, thecounters reset and the sequence begins again starting with a responsefrom the sensor with address 1.

Referring to FIG. 14, controller 20 can send a reset command 1402instructing all the sensors to reset their counters. The reset command1402 may be a pulse (high or low) on the bus having a predeterminedduration. In the example of FIG. 14, after the sensor with address 2sends data 1404, the reset signal 1402 appears on the bus and all thesensors' counters are reset so that the sequence restarts from thebeginning Thus, in response to the next trigger pulse 1406 sent bycontroller 20, the first sensor in the sequence (i.e. sensor 1) respondsby sending data 1408 to controller 20. After the next trigger pulse, thenext sensor in the sequence (i.e. sensor 2) sends data, and so on.

Referring to FIG. 15, the sensors may be configured to delay sendingtheir response by a predetermined time corresponding to the address ofthe sensor. For example, in response to the first trigger pulse 1502,the sensor with address 1 may delay for time T1 before sending response1504. Similarly, in response to the second trigger pulse 1506, thesensor with address 2 may delay for a time T2 before sending response1508. Likewise, the sensor with address 3 may delay by a time T3, thesensor with address 4 may delay by a time T4, etc. Each delay time (alsoreferred to as a delay time period) T1-TN may have a unique durationthat can be used by controller 20 and/or the sensors to identify thesensor that sent the response. For example, if one sensor fails torespond to a request, controller 20 can identify the source of thesubsequent response and determine that the sequence has fallen out oforder. The controller may then reset the sensors (as described above),generate an error message, or take any other appropriate action.

Additionally or alternatively, if, for example, a sensor is notobserving the bus for some time or does not receive or does not processone or more trigger pulses sent by controller 20 it may lose count ofthe sequence. In this situation, the sensor may read the delay time fromthe other sensors' responses to determine which sensor is currentlyresponding to controller 20. Based on the current response, the sensormay determine when it should respond to controller 20. Assume, forexample, that sensor 6 was not able to observe one or more triggerpulses from controller 20 due to interference and lost its count. Assumealso that controller 20 sends a trigger pulse and that sensor 3responds. Sensor 6 may observe sensor 3's response, read the delay time,and based on the delay time, determine that sensor 3 just responded.Sensor 6 may then reset its counter to 3 so that it has a proper countof the sequence, and so that it can respond to the sixth trigger pulsein the sequence when the time comes. This may eliminate or reduce theneed for controller 20 to reset the sensors if one or more sensors losetheir place in the sequence.

Referring to FIG. 16, the sensors may be configured to take ameasurement at a predetermined point within the sequence. In anembodiment, after the sequence starts or restarts and controller 20sends the first trigger pulse 1602 in the sequence, all the sensors onthe bus may perform a measurement (as described above). The sensors maybe configured to take a measurement at any point during the sequence,for example, at the end of the sequence, at a point in the middle of thesequence, etc.

In another embodiment, each sensor may be configured to take ameasurement at a different point in the sequence. The sensor withaddress 2, for example, may be configured to take a measurement afterthe first trigger 1602 so that, by the time the second trigger 1604 isreceived, the sensor with address 2 has newly sampled data it can sendto controller 20. Similarly, the sensor with address 3 may be configuredto take a measurement after the second trigger, the sensor with address4 after the third trigger, etc.

Referring now to FIG. 17, in another embodiment, controller 20 may senda synchronous sample pulse 1702 to the sensors at the beginning of thesequence 1700. Synchronous sample pulse 1702 may be a command which,when received by the sensors, may instruct all the sensors to make ameasurement, as described above. To send synchronous sample pulse 1702,controller 20 may hold the bus low (or alternatively high) for apredetermined amount of time. The duration of synchronous sample pulse1702 may be different from that of the reset pulses described above sothat the sensors can differentiate the different types of pulses.

Referring to FIG. 18, the synchronous sample pulse need not appear atthe beginning of the sequence, and can be inserted between any triggerpulse sent by the controller and/or response sent by a sensor. As shownin FIG. 18, controller 20 may insert a synchronous sample pulse 1802after a response 1804 from the sensor with address 1. Controller 20 mayalso insert a synchronous sample pulse at any point in the sequence.

In an embodiment, synchronous sample pulse 1802 can replace a triggerpulse, such as trigger pulse 1806 or 1808 for example. In FIG. 18,synchronous sample pulse 1802 has replaced the trigger pulse that wouldotherwise appear in the second position in sequence 1800. In thisexample, synchronous trigger pulse 1802 may perform two functions—it mayact as a synchronous trigger pulse causing all the sensors on the bus totake a measurement, and also act as a trigger instructing the nextsensor in the sequence to send its data to controller 20. Inembodiments, synchronous sample pulse 1802 can be used to replace anytrigger pulse in the sequence.

Referring now to FIG. 19, a transmission sequence 1900 includes adiagnostic pulse 1902. Controller 20 may transmit diagnostic pulse 1102by holding the bus low (or alternatively high) for a predeterminedduration. The duration of diagnostic pulse 1102 may be different fromthe duration of synchronous sample pulse 1702 and reset pulse 1402 todifferentiate the type of pulses. Diagnostic pulse 1902 may be a commandwhich, when received by the sensors, instructs each sensor to performself-diagnostic tests to determine whether the sensor is operatingproperly. To allow the sensors enough time to perform diagnostic tests,diagnostic pulse 1902 may be followed by diagnostic time 1904, duringwhich time controller 20 does not send any additional requests. Theduration of diagnostic time 1904 may be a predetermined time sufficientto allow the sensors to perform and complete their diagnostic tests.

Following diagnostic time 1904, controller 20 may begin sending triggerpulses (e.g. trigger pulse 1906) to the sensors, which may respond bysending data to controller 20 if the position of the trigger pulsewithin sequence 1900 matches the address of the sensor, as describedabove. After receiving diagnostic pulse 1902, the next data transmissionsent by each sensor may include the results of the self-diagnostic testperformed by the sensor.

In some embodiments, controller 20 may send diagnostic pulse 1902 at thebeginning of sequence 1900. In this case, the diagnostic pulse may alsoact as a reset command; when the sensors receive the diagnostic pulsethey may reset their counters so that the transmission sequence startsanew. In other embodiments, controller 20 may send a diagnostic pulse inthe middle of the transmission sequence.

Referring to FIG. 20, transmission sequence 2000 provides an example ofcontroller 20 sending a diagnostic pulse 2002 in the middle of thetransmission sequence. In this example, the diagnostic pulse 2002 may beused to instruct a single sensor to perform self-diagnostic tests.Controller 20 sends a trigger pulse 2004 and receives data 2006 fromsensor 1. Following data 2006, controller 20 sends diagnostic pulse 2002in place of the trigger pulse that would otherwise follow data 2006.Because diagnostic pulse 2002 appears in the second position of thesequence, sensor 2 may receive diagnostic pulse 2002 and initiate itsself-diagnostic tests. Any other sensors on the bus may continue tooperate normally without initiating self-diagnostic tests because thediagnostic pulse only appeared in position 2 of the sequence.

As noted above, performing self-diagnostic tests may require extra time.Thus, sensor 2 will not respond immediately to controller 20 by sendingits self-diagnostic test results. Rather, sensor 2 may respond with itstest results after the sequence restarts. Note that in this example,there are four sensors operating on the bus. Therefore, after fourtrigger pulses, the sequence will restart. Thus, while sensor 2 isperforming self-diagnostic tests, controller 20 may continue to transmittrigger pulses (e.g. trigger pulses 2008 in position 3 of the sequence,2010 in position 4 of the sequence) and receive data from the sensors.

The next trigger pulse 2012 is in position 1 and restarts thetransmission sequence. Thus, sensor 1 responds to trigger pulse 2012 bysending data 2018. The next trigger pulse 2020 instructs sensor 2 tosend its data. Because sensor 2 initiated self-diagnostic tests inresponse to diagnostic pulse 2002 in the previous sequence, sensor 2 mayrespond to trigger pulse 2020 by sending data 2022, which may includeresults from sensor 2's self-diagnostic tests.

In other embodiments, a diagnostic pulse 2002 in the middle of thetransmission sequence may cause all sensors on the bus to initiateself-diagnostic tests.

Referring now to FIG. 21, controller 20 may send a counter reset pulse2102 to the sensors by holding the bus low (or alternatively high) for apredetermined period of time. The duration of counter reset pulse 2102may be different from that of the diagnostic pulses, trigger pulses, orother pulses described above so as to differentiate the counter resetpulse 2102 from the other types of pulses.

Counter reset pulse 2102 may act as a reset command and may betransmitted at any point in transmission sequence 2100. When received bythe sensors, the sensors may reset their counters so that thetransmission sequence 2100 may restart from the beginning As shown inFIG. 21, reset pulse 2102 is sent after sensor 1 has transmitted data2104. Reset pulse 2102 then causes transmission sequence 2100 to restartso that the next trigger pulse 2106 is the first trigger pulse in thesequence, and the following data 2108 is again sent by sensor 1.

Having described various embodiments, which serve to illustrate variousconcepts, structures and techniques, which are the subject of thispatent, it will now become apparent to those of ordinary skill in theart that other embodiments incorporating these concepts, structures andtechniques may be used.

Accordingly, it is submitted that that scope of the patent should not belimited to the described embodiments but rather should be limited onlyby the spirit and scope of the following claims. Elements of differentembodiments described herein may be combined to form other embodimentsnot specifically set forth above.

What is claimed is:
 1. A network slave device comprising: a transceiverfor communicating over a communication bus in accordance with apoint-to-point network protocol; an address to identify the networkslave device; and a communication circuit configured to process a seriesof commands received by the transceiver and respond to a command if aposition of the command in the series of commands corresponds to theaddress of the network slave device.
 2. The network slave device ofclaim 1 wherein the point-to-point communication protocol is a SENTprotocol.
 3. The network slave device of claim 1 further comprising amemory, wherein the address is stored in the memory.
 4. The networkslave device of claim 1 wherein the slave device comprises a magneticfield sensor.
 5. The network slave device of claim 4 wherein themagnetic field sensor comprises magnetic field sensing elements.
 6. Thenetwork slave device of claim 5 wherein the magnetic field sensingelements Hall effect elements.
 7. The network slave device of claim 5wherein the magnetic field sensing elements comprise magnetoresistiveelements.
 8. The network slave device of claim 7 wherein themagnetoresistive elements comprise a GMR element, a TMR element, an MTJelement, a spin-valve, or a combination thereof.
 9. The network slavedevice of claim 4 wherein the commands comprise requests for datarepresenting a magnetic field detected by the magnetic field sensor. 10.The network slave device of claim 1 further comprising a counterconfigured to count the number of commands sent by the master device.11. The network slave device of claim 10 further configured to respondto a reset command by resetting the counter.
 12. The network slavedevice of claim 10 further configured to reset the counter when a numberof commands received meets or exceeds a number of slave devices coupledto the communication bus.
 13. The network slave device of claim 1wherein the commands include one or more of: a sample command to performa measurement; a data request command to send measurement data; adiagnostic command perform a self-test; a reset command to reset acounter; or a combination thereof.
 14. The network slave device of claim13 wherein the sample command comprises a pulse of one predeterminedlength, the diagnostic command comprises a pulse of a secondpredetermined length; the data request command comprises a pulse of athird predetermined length; and the reset command comprises a pulse of afourth predetermined length.
 15. The network slave device of claim 1wherein the commands comprise broadcast commands.
 16. The network slavedevice of claim 15 wherein the broadcast commands include one or moreof: a sample command to perform one or more respective measurements; adiagnostic command to perform one or more respective self-tests; a resetcommand to reset a counter of the slave device; or a combinationthereof.
 17. The network slave device of claim 1 further configured todelay sending a response to the commands by a delay time periodcorresponding to the address of the slave device.
 18. The network slavedevice of claim 1 further configured to read a delay time period of aresponse from another network slave device and determine a currentposition in the series based on the delay time period.
 19. A systemcomprising: a master device coupled to a communication bus andconfigured to communicate over the communication bus in accordance witha point-to-point communication protocol to send a series of commandsover the communication bus; and one or more slave devices coupled to thecommunication bus to communicate over the communication bus inaccordance with the point-to-point communication protocol, each of theslave devices having a respective address to identify the respectiveslave device and configured to respond to a command in the series ofcommands that has a position within the series that matches therespective address of the respective slave device.
 20. The system ofclaim 19 wherein the master device and the one or more slave devices areconfigured to communicate over the communication bus in accordance witha point-to point communication protocol.
 21. The system of claim 20wherein the point-to-point communication protocol is a SENT protocol.22. The system of claim 19 wherein the one or more slave devices aremagnetic field sensors.
 23. The system of claim 22 wherein the commandscomprise requests for data representing a magnetic field detected by atleast one of the magnetic field sensors.
 24. The system of claim 19wherein the one or more slave devices each comprise a counter configuredto count the number of commands sent by the master device.
 25. Thesystem of claim 24 wherein the master device is configured to send areset command which, when received by the one or more slave devices,resets the counters of the one or more slave devices.
 26. The system ofclaim 24 wherein each respective slave device is configured to respondto the commands when a counter of the respective slave device matchesthe address of the respective slave device.
 27. The system of claim 24wherein the one or more slave devices are configured to reset theircounters when a number of commands sent by the master device matches orexceeds a number of slave devices coupled to the communication bus. 28.The system of claim 19 wherein the commands include one or more of: asample command to perform a measurement; a diagnostic command perform aself-test; and a reset command to reset a counter.
 29. The system ofclaim 28 wherein the sample command comprises a pulse of onepredetermined length, the diagnostic command comprises a pulse of asecond predetermined length; and the reset command comprises a pulse ofa third predetermined length.
 30. The system of claim 19 wherein themaster device is further configured to send broadcast commands to allthe slave devices coupled to the communication bus.
 31. The system ofclaim 30 wherein the broadcast commands comprise commands that do notinclude an address.
 32. The system of claim 30 wherein the broadcastcommands include one or more of: a sample command instructing all therespective slave devices to perform one or more respective measurements;a diagnostic command instructing all the respective slave devices toperform one or more respective self-tests; and a reset commandinstructing all the respective slave device to reset respective countersof the respective slave devices.
 33. The system of claim 19 wherein theslave devices are configured to delay sending a response to the commandsby a time period corresponding to the address of the slave device. 34.The system of claim 19 wherein the slave devices are configured to reada delay time period of a response from another slave device anddetermine a current position in the series based on the delay timeperiod.
 35. A method comprising: sending a series of commands by amaster device coupled to a one-wire communication bus; and responding toone of the commands, by a selected slave device, if the position of thecommand in the series of commands matches an address of the selectedslave device.
 36. The method of claim 35 wherein the master device andthe one or more slave devices are configured to communicate over thecommunication bus in accordance with a point-to point communicationprotocol.
 37. The method of claim 36 wherein the point-to-pointcommunication protocol is a SENT protocol.
 38. The method of claim 35wherein the one or more slave devices are magnetic field sensors. 39.The method of claim 38 wherein sending the series of commands comprisessending requests for data representing a magnetic field detected by atleast one of the magnetic field sensors.
 40. The method of claim 35further comprising counting the commands by the one or more slavedevices coupled to the communication bus;
 41. The method of claim 40wherein counting the commands comprises incrementing respective countersof the one or more slave devices.
 42. The method of claim 35 furthercomprising sending, by the master device a reset command which, whenreceived by the one or more slave devices, resets the respectivecounters.
 43. The method of claim 42 further comprising restarting thecount a number of commands sent by the master device matches or exceedsa number of slave devices coupled to the communication bus.
 44. Themethod of claim 35 wherein the sending the commands include sending oneor more of: a sample command to perform a measurement; a data requestcommand to send measurement data; a diagnostic command to perform aself-test; and a reset command to reset a counter.
 45. The method ofclaim 44 wherein sending the sample command comprises sending a pulse ofone predetermined length, sending the diagnostic command comprisessending a pulse of a second predetermined length; sending the datarequest command comprises sending a pulse of a third predeterminedlength; and sending the reset command comprises sending a pulse of afourth predetermined length.
 46. The method of claim 35 furthercomprising sending broadcast commands to all the slave devices coupledto the communication bus.
 47. The method of claim 46 wherein thebroadcast commands comprise commands that do not include an address. 48.The method of claim 46 wherein sending the broadcast commands includessending one or more of: a sample command instructing all the respectiveslave devices to perform one or more respective measurements; adiagnostic command instructing all the respective slave devices toperform one or more respective self-tests; and a reset commandinstructing all the respective slave device to reset respective countersof the respective slave devices.
 49. The method of claim 35 whereinresponding comprises delaying sending a response to the commands by adelay time period corresponding to the address of the slave device. 50.The method of claim 35 further comprising reading, by the network slavedevice, a delay time period of a response from another network slavedevice and determining a current position in the series based on thedelay time period.